Skip to content

feat(core): Make sure Supabase db query insights are populated #16169

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
May 28, 2025

Conversation

smeubank
Copy link
Member

DB must be set to populate query/database insights

DB must be set to populate query/database insights
@smeubank smeubank requested a review from onurtemizkan April 30, 2025 06:23
@smeubank
Copy link
Member Author

@onurtemizkan this is to ensure that the db query insights is populated, the logic is not quite right in the product IMO. But setting only db for the span op is fine and the sentry.op will have db.{crud-op}

I just investigated this with cursor. Could you take over this PR to make sure it is correct, please?

Develop docs are a bit wrong

@onurtemizkan onurtemizkan changed the title Update to always set db feat(core): Make sure Supabase db query insights are populated May 28, 2025
@onurtemizkan onurtemizkan marked this pull request as ready for review May 28, 2025 11:10
@AbhiPrasad AbhiPrasad merged commit ff7ab11 into develop May 28, 2025
158 checks passed
@AbhiPrasad AbhiPrasad deleted the fix(span.op)supabase-db-op branch May 28, 2025 15:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants